pm˜ F„¤Fm›˜ —z›¨˜ m'›"dd"›apm˜%˜ pmOaV - Public Support Login ...

Planning Your ORACLE SIDs and Griffin Universes
Valid names A C1 HB Z9
Invalid names ABC aB Ab 1A
Note: Do not use the same name for an ORACLE SID and a Griffin Universe.
Choosing Names and Sizes of Tablespaces and Database Files
Structures in the LINC Database are assigned to disk locations according to Tablespace
name. The disk locations available to a given Tablespace are determined by the ORACLE
or Griffin database files the Tablespace contains.
You may want to separate files from each other for reasons of hardware failure and I/O
load. For example, you can put audit and control files on a different physical disk unit from
the rest of the database. You can improve performance by placing high-usage files on
physical disk units of their own, reducing I/O contention, and placing the files in such a
way as to reduce head movement.
For the initial installation, most Tablespaces normally consist of a single ORACLE or
Griffin database file, unless there is insufficient available contiguous space. More database
files can be added subsequently to Tablespaces as required.
v A-3