<BETA>

The task is to create a new instance named abc.

It is assumed that the Oracle software is already loaded, and that:

ORACLE_BASE=/oracle
ORACLE_HOME=/oracle/product/8.1.7

We have be given 2 spindles (/abc/v001, and /abc/v002) to work with.

• Some convinces
• Create the OFA file system for instance abc.
• Create the initabc.ora file.
• Create the abc instance.

Some convinces:

By creating the following alias(s) you can be sure you are running server manager against the appropriate instance:

alias smabc='export ORACLE_SID=abc; svrmgrl'

This is also handy: create a file ci.sql that contains: connect internal. Now you can sign on to a instance abc by:

smabc
@ci

Create the OFA file system for abc:

cd /oracle/admin
mkdir abc
cd abc
mkdir adhoc
mkdir arch
mkdir bdump
mkdir cdump
mkdir create
mkdir exp
mkdir logbook
mkdir pfile
mkdir udump

The OFA file system is now ready.

Create the initabc.ora file:

Oracle supplies an init.ora file. With current standard disk sizes (9M-18M), and memory sizes (~1G), this is a file that is showing it's age.
I am not a big fan if the ifile= parameter.
My starting point is initabc.ora. In this file the parameters are placed in approximate order of importance or significance.
It is simple and can be used to spawn subsequent instances.

Further comments:

• The instance size is approximately :
  • db_block_buffers * db_block_size
  • shared_pool_size
  • java_pool_size
  • sum of above * 1.2
• leave timed_statistics on. It provides valuable info and if its effecting your system you probably need more resources any way.
• Indenting all parameter 2 spaces makes it easy to comment/uncomment params during experimentation.

Thus to initabc.ora is ready.

Create the abc instance:

cd /oracle/admin/abc/create

Place the file s00 into the create directory.

Modify the default characteristics of this file to reflect your instance profile (file locations, sizes, redo logs, rollbacks ...):

TABLESPACE NAME	FILE NAME	SIZE (M)
SYSTEM	/abc/v001/SYSTEM_0.dbf	200
RBS001	/abc/v001/RBS001_0.dbf	200
RBS002	/abc/v002/RBS002_0.dbf	200
RBS003	/abc/v001/RBS003_0.dbf	200
RBS004	/abc/v002/RBS004_0.dbf	200
RBS005	/abc/v001/RBS005_0.dbf	200
RBS006	/abc/v002/RBS006_0.dbf	200
TEMP	/abc/v002/TEMP_0.dbf	1000
USERS	/abc/v002/USERS_0.dbf	200
TOOLS	/abc/v002/TOOLS_0.dbf	200

Now edit this file into s01.sql, s02.sql, ... s05.sql.
It would be possible to just run a s00.sql, but its just a little more judicious to break it into parts.
Note that the s00 file can be used as a starting point for creating other instances later.
Now run:

smabc
@ci
@s01
@s02
@s03
@s04
@s05
... (now set sys,system passwords)
alter user sys    identified by abcdba;
alter user system identified by abcdba;     

Back