6
Post-Installation Database Creation

Delete a Database

The Delete a Database option of Oracle Database Configuration Assistant lets you quickly and easily delete all database files including the initialization parameter file.

Using BUILD_DB.SQL

This section describes how to create a new database manually using a SQL script. There are a number of ways to create a database depending on if you want to:

• Make a copy of an existing database and remove the old database.

• Make a copy of an existing database and keep the old database.

• Create a new database when no database exists on your system that you can copy.

The following table summarizes the steps involved in creating a new database for each of these database creation scenarios. Each step is explained in detail in the following subsections.

Perform these tasks...	If you want to...
	Copy an existing database to a new database, then remove the old database	Copy an existing database to a new database, then keep the old database	Create a new database when no other database exists on your system
Exporting an Existing Database	Yes	Only if you want to copy data from the existing database to the new database	Not applicable
Deleting Database Files	Yes	No	Not applicable
Modifying the INIT.ORA File	Yes	Yes	Yes
Creating and Starting an Oracle Instance	No	Yes	Yes
Putting the CREATE DATABASE Statement in a Script	Yes	Yes	Yes
Creating a Database	Yes	Yes	Yes
Importing a Database	Yes	Only if you want to import tables and other objects exported from the existing database	Not applicable
Updating the ORACLE_SID in the Registry	No	Only if you want to change the default SID	Yes
Backing Up the New Database	Yes	Yes	Yes

How to Create a Database

An example is used in the following sections to demonstrate how to create a database.

In this example, you will copy an existing database (the starter database with a SID of ORCL located in the C:\ORACLE\ORADATA\ORCL directory) to a new database with a database name and SID of PROD located in the C:\ORACLE\ORADATA\PROD directory.

You will delete the starter database ORCL after you have created the PROD database.

Creating Directories

Create the following directories in which to put the administration and database files for the new database PROD:

• C:\ORACLE\ADMIN\PROD

• C:\ORACLE\ADMIN\PROD\BDUMP

• C:\ORACLE\ADMIN\PROD\PFILE

• C:\ORACLE\ADMIN\PROD\UDUMP

• C:\ORACLE\ORADATA\PROD

Exporting an Existing Database

You only need to export an existing database if you want to copy its contents to a new database.

You can invoke the Export Utility by using either parameter mode or interactive mode. However, parameter mode is the recommended mode. Interactive mode provides less functionality than parameter mode and exists for backward compatibility only.

Example 6-1 Parameter Mode

C:\> EXP SYSTEM/PASSWORD FILE=MYEXP.DMP FULL=Y LOG=MYEXP.LOG

Example 6-2 Interactive Mode

C:\> EXP SYSTEM/PASSWORD

Enter only the command EXP SYSTEM/PASSWORD to begin an interactive session and let the Export Utility prompt you for the information it needs.

See Oracle8i Utilities for more information on using the Export Utility.

To export all data from an existing database to a new database:

1. Set ORACLE_SID to the database service of the database whose contents you want to export. For example, if the database you want to export is the starter database ORCL, enter the following at the MS-DOS command prompt. Note that there are no spaces around the equal sign (=) character.

   C:\> SET ORACLE_SID=ORCL
   

2. Start the Export Utility from the MS-DOS command prompt:

   C:\> EXP SYSTEM/PASSWORD FILE=MYEXP.DMP FULL=Y LOG=MYEXP.LOG
   

   You now have a full database export of the starter database ORCL in the file MYEXP.DMP. All messages from the Export Utility are logged in the file MYEXP.LOG.

Deleting Database Files

Deleting database files is only required when you want to copy an existing database to a new database to replace the old database. In the following example, you delete the database files of the starter database ORCL.

To delete database files:

1. Shut down the starter database ORCL using OSTOP

2. Delete the following database files located in the C:\ORACLE\ORADATA\ORCL directory:
   • CONTROL01.CTL

   • CONTROL02.CTL

   • CONTROL03.CTL

   • INDX01.DBF

   • DR01.DBF

   • RBS01.DBF

   • SYSTEM01.DBF

   • TEMP01.DBF

   • USERS01.DBF

   • REDO01.LOG

   • REDO02.LOG

   • REDO03.LOG

   • TOOLS01.DBF

Modifying the INIT.ORA File

If you are using the starter database ORCL as the basis for your new database, copy INIT.ORA file:

C:\ORACLE\ORACLE_HOME\ADMIN\ORCL\PFILE\INIT.ORA 

to

C:\ORACLE\ORACLE_HOME\ADMIN\PROD\PFILE\INIT.ORA 

and modify the file as described in this section.

If you do not have an existing database on your system, you cannot copy an initialization parameter file to use as the basis for your new INIT.ORA file. However, you can use the sample initialization parameter file INITSMPL.ORA provided in the ORACLE_BASE\ORACLE_HOME\ADMIN\SAMPLE\PFILE directory as the basis for the INIT.ORA file for the PROD database.

If you use INITSMPL.ORA as the basis for the INIT.ORA file, you must modify the following initialization parameters in the INIT.ORA file, or you will not be able to start the PROD database:

• DB_NAME

• INSTANCE_NAME

• SERVICE_NAMES

• CONTROL_FILES

• BACKGROUND_DUMP_DEST

• USER_DUMP_DEST

Modifying the DB_FILES initialization parameter is recommended to optimize performance.

Creating and Starting an Oracle Instance

You only need to create and start an Oracle instance if you want to do one of the following:

• Copy an existing database to a new database and keep the old database

• Create a new database when no other database exists on your system that you can copy

To create an Oracle instance:

1. Run ORADIM from the MS-DOS command prompt:

   C:\> ORADIM -NEW -SID PROD -INTPWD PASSWORD -STARTMODE MANUAL
   -PFILE C:\ORACLE\ADMIN\PROD\PFILE\INIT.ORA  -ORA_REQ_HOME HOME_NAME
   

   Note that the previously-created INIT.ORA file is specified, with complete path, including drive name.

2. Set ORACLE_SID to equal PROD. Note that there are no spaces around the equal sign (=) character:

   C:\> SET ORACLE_SID=PROD
   

Putting the CREATE DATABASE Statement in a Script

The CREATE DATABASE statement is a sequence of SQL statements that creates the database. Create a script containing this statement that you can reuse anytime you want to create a database.

Open the BUILD_DB.SQL script located in C:\ORACLE\ORA81\RDBMS\ADMIN and save it as BUILD_PROD.SQL.

This file becomes the basis for your script.

To prepare the CREATE DATABASE script:

Make the following changes to the BUILD_PROD.SQL script.

1. Set PFILE so it points to the C:\ORACLE\ADMIN\PROD\PFILE\INIT.ORA initialization file.

2. Change CREATE DATABASE SAMPLE to CREATE DATABASE PROD.

3. Change all occurrences of SAMPLE to PROD. For example, change C:\ORACLE\ORADATA\SAMPLE\REDO01.LOG to C:\ORACLE\ORADATA\PROD\REDO01.LOG

The following is the sample BUILD_DB.SQL script. Areas that you must modify to create a database called PROD are highlighted.

--
-- This file must be run out of the directory containing the
-- initialization file.

startup nomount pfile=C:\Oracle\ADMIN\SAMPLE\pfile\initsmpl.ora

--  Create database

create database SAMPLE
    controlfile reuse
    logfile 'C:\Oracle\ORADATA\SAMPLE\redo01.log' size 1M reuse,
            'C:\Oracle\ORADATA\SAMPLE\redo02.log' size 1M reuse,
            'C:\Oracle\ORADATA\SAMPLE\redo03.log' size 1M reuse
                datafile 'C:\Oracle\ORADATA\SAMPLE\system01.dbf' size 10M reuse 
autoextend on
next 10M maxsize 200M 
character set WE8ISO8859P1;

create rollback segment rb_temp storage (initial 100 k next 250 k);

-- Create additional tablespaces ...

-- USERs: Create user sets this as the default tablespace
-- TEMP: Create user sets this as the temporary tablespace
-- RBS: For rollback segments

create tablespace users
    datafile 'C:\Oracle\ORADATA\SAMPLE\users01.dbf' size 3M reuse autoextend on
      next 5M maxsize 150M;
create tablespace rbs
    datafile 'C:\Oracle\ORADATA\SAMPLE\rbs01.dbf' size 5M reuse autoextend on
      next 5M maxsize 150M;
create tablespace temp
    datafile 'C:\Oracle\ORADATA\SAMPLE\temp01.dbf' size 2M reuse autoextend on
      next 5M maxsize 150M;
create tablespace oem_repository
    datafile 'C:\Oracle\ORADATA\SAMPLE\oemrep01.dbf' size 3M reuse autoextend on
      next 5M maxsize 150M;
create tablespace indx;
    datafile 'C:\Oracle\ORADATA\SAMPLE\indx01.dbf' size 2M reuse autoextend on
      next 5M maxsize 150M;
--      next 5M maxsize 150M;
alter rollback segment rb_temp online;

-- Change the SYSTEM users' password, default tablespace and
-- temporary tablespace.

alter user system temporary tablespace temp;
alter user system default tablespace users;

-- Create 16 rollback segments.  Allows 16 concurrent users with open
-- transactions updating the database. This should be enough.

create public rollback segment rb1 storage(initial 50K next 250K)
  tablespace rbs;
create public rollback segment rb2 storage(initial 50K next 250K)
  tablespace rbs;
create public rollback segment rb3 storage(initial 50K next 250K)
  tablespace rbs;
create public rollback segment rb4 storage(initial 50K next 250K)
  tablespace rbs;
create public rollback segment rb5 storage(initial 50K next 250K)
  tablespace rbs;
create public rollback segment rb6 storage(initial 50K next 250K)
  tablespace rbs;
create public rollback segment rb7 storage(initial 50K next 250K)
  tablespace rbs;
create public rollback segment rb8 storage(initial 50K next 250K)
  tablespace rbs;
create public rollback segment rb9 storage(initial 50K next 250K)
  tablespace rbs;
create public rollback segment rb10 storage(initial 50K next 250K)
  tablespace rbs;
create public rollback segment rb11 storage(initial 50K next 250K)
  tablespace rbs;
create public rollback segment rb12 storage(initial 50K next 250K)
  tablespace rbs;
create public rollback segment rb13 storage(initial 50K next 250K)
  tablespace rbs;
create public rollback segment rb14 storage(initial 50K next 250K)
  tablespace rbs;
create public rollback segment rb15 storage(initial 50K next 250K)
  tablespace rbs;
create public rollback segment rb16 storage(initial 50K next 250K)
  tablespace rbs;

You will run this script at the SQL*Plus prompt in "Creating a Database".

Creating a Database

To use the BUILD_PROD.SQL script to create a database:

1. Make PROD the current SID:

   C:\> SET ORACLE_SID=PROD
   

2. Start SQL*Plus from the MS-DOS command prompt, and connect to the database as INTERNAL:

   C:\> SQLPLUS
   SQL> CONNECT INTERNAL/PASSWORD 
   

The password is the one that you used to create the service, with the ORADIM -NEW command in "Creating and Starting an Oracle Instance".

The message Connected appears.

SQL> SPOOL BUILD_PROD.LOG

SQL> @C:\ORACLE\ORA81\RDBMS\ADMIN\BUILD_PROD.SQL;

If the database is created successfully, the instance is started and the message Statement processed appears numerous times.

If you receive any errors, there are three possible causes, as illustrated below.

Cause	Solution
The BUILD_PROD.SQL script contains syntax errors.	Correct them.
Some of the files to be created by the BUILD_PROD.SQL script already exist in the file system.	Make sure you are not using any file names already used by another database on the system.
An error occurred at the operating system level, such as a file or directory permission problem.	You should have received a series of errors in SQL*Plus, the last one of which should have the OSD- prefix. At the end of the OSD error, you typically see an operating system error number in parentheses. To see what the error means, do either of the following: From the MS-DOS command prompt, enter: C:\> NET HELP n or From the SQL*Plus prompt, enter: SQL> HOST NET HELP n where n is the operating system error number.

You must correct these problems before making another attempt to create a database.

SQL> @C:\ORACLE\ORA81\RDBMS\ADMIN\CATALOG.SQL;

SQL> @C:\ORACLE\ORA81\RDBMS\ADMIN\CATPROC.SQL;

SQL> SPOOL OFF

SQL> EXIT

Importing a Database

You can import the full export created in "Exporting an Existing Database" into the new database.

You can also invoke the Import Utility, using parameter mode or interactive mode. Parameter mode is recommended, because interactive mode provides less functionality. Interactive mode exists solely for backward compatibility.

Example 6-3 Parameter Mode

C:\> IMP SYSTEM/PASSWORD FILE=MYEXP.DMP FULL=Y LOG=MYEXP.LOG

Example 6-4 Interactive Mode

C:\> IMP SYSTEM/PASSWORD

Enter only the command IMP SYSTEM/PASSWORD to begin an interactive session and let the Import Utility prompt you for the information it needs.

See Oracle8i Utilities for more information on using the Import Utility.

To import a database:

• Run the Import Utility:

  C:\> IMP SYSTEM/PASSWORD FILE=MYEXP.DMP FULL=Y LOG=MYIMP.LOG 
  

  IMPORTANT: If the original database from which the export file was generated contains tablespaces that are not in the new database, the Import Utility tries to create those tablespaces with associated data files. The easy solution is to ensure that both databases contain the same tablespaces. The data files do not have to be identical. Only the tablespace names are important.

Updating the ORACLE_SID in the Registry

If this is the first database on the system or if you want to make the new database the default database, you must make a change in the registry.

1. Start the registry editor at the MS-DOS command prompt:

   C:\> REGEDIT
   

   The registry editor window appears.

2. Choose the \HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME0 subkey for the first Oracle home on your computer. For subsequent installations to different Oracle homes on the same computer, the path is \HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEID, where ID is the unique number identifying the Oracle home.

   See Also: See Appendix C, "Oracle8i Configuration Parameters and the Registry" for more information on the subkey locations for multiple Oracle homes.

3. Locate the ORACLE_SID parameter on the right side of the registry editor window.

4. Double-click the parameter name and change the data to the new SID, which is PROD in this example.

If you do not yet have the ORACLE_SID parameter, because this is the first database on your system, you must create it.

Backing Up the New Database

To back up the new database:

1. Shut down the database instance using OSTOP

   See "Starting and Shutting Down a Database Using OSTART and OSTOP" for more information on how to use OSTART and OSTOP.

2. Using the tool of your choice, back up the database files.
   Database files consist of the initialization parameter file, control files, online redo log files, and data files.

   When the backup is complete, you can start the database again, create users and objects, if necessary, make any other changes, and use the database.

   Be sure to back up the database backup after making any significant changes to the database, such as switching the ARCHIVELOG mode, or adding a tablespace or data file.

   See Also:: Chapter 9, "Backing Up and Recovering Database Files", Oracle8i Concepts, Oracle8i Backup and Recovery Guide, and Oracle8i Administrator's Guide for more information on archiving and backup/recovery.

   Warning:: Do not store database files on a compressed drive. This can result in write errors and decreased performance.